Fix pylint 1.7.2 no-else-return issues#8361
Merged
Merged
Conversation
|
@balloob, thanks for your PR! By analyzing the history of the files in this pull request, we identified @wmalgadey, @armills and @fabaff to be potential reviewers. |
Merged
dethpickle
pushed a commit
to dethpickle/home-assistant
that referenced
this pull request
Aug 18, 2017
* Fix pylint 1.7.2 no-else-return issues * Update tomato.py
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
This fixes all
no-else-returnissues raised by PyLint 1.7.2Related issue (if applicable): #7108
Checklist:
If the code does not interact with devices:
toxrun successfully. Your PR cannot be merged unless tests pass